This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Suggested edits to further conform to ISO 8601 temporal standards #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I also aligned accrualPeriodicity to align with http://www.ukoln.ac.uk/metadata/dcmi/collection-DCCDAccrualPeriodicity/. Forgot to branch separately before committing so it got wrapped up in this as well. |
|
Wanted to reopen this as it looks like no commits have been pulled in. |
|
Replacing this with #116 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It looks like this has been brought up before in (#43) but a solid commit was not made to align fully with the ISO 8601 standard. I suggest expressing datetimes as
YYYY-MM-DDTHH:MM:SSZand ranges asYYYY-MM-DDTHH:MM:SSZ/YYYY-MM-DDTHH:MM:SSZ.